Skip to content

docs: clarify useApi returns loader state at top level - #87

Closed
VldMrgnn wants to merge 1 commit into
fxforge:mainfrom
VldMrgnn:fix/issue-49-jsdoc-clarity
Closed

VldMrgnn wants to merge 1 commit into
fxforge:mainfrom
VldMrgnn:fix/issue-49-jsdoc-clarity

Conversation

@VldMrgnn

Copy link
Copy Markdown
Collaborator

Fixes #49

  • Add note in useApi JSDoc that loader fields are returned at top level
  • Update useLoaderSuccess examples to use api object directly
  • Remove confusion about nested loader property"

@github-actions

Copy link
Copy Markdown
Contributor

Package Changes Through 00299e2

No changes.

Add a change file through the GitHub UI by following this link.


Read about change files or the docs at github.com/jbolda/covector

@pkg-pr-new

pkg-pr-new Bot commented Mar 24, 2026

Copy link
Copy Markdown
More templates

npm i https://pkg.pr.new/starfx@87

commit: 00299e2

@VldMrgnn
VldMrgnn requested a review from jbolda March 26, 2026 00:15
Comment thread src/react.ts
@VldMrgnn

Copy link
Copy Markdown
Collaborator Author

Closing this. @jbolda 's question made me look at it again more carefully. Both patterns are valid and the destructuring isn't actually misleading.

@VldMrgnn VldMrgnn closed this Mar 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

clarification needed: should useApi export full loader or should useLoaderSuccess JSDoc be updated?

2 participants